home *** CD-ROM | disk | FTP | other *** search
- Date: Fri, 29 Jul 1994 08:43:20 -0400 (EDT)
- From: Rick Flashman <rflashma@mhc.mtholyoke.edu>
- Subject: RE: Re: Scope of an APP_DEFS file
- To: gem-list@world.std.com
- In-Reply-To: <9407290748.AA09473@getafix.oasis.icl.co.uk>
- Message-Id: <Pine.3.89.9407290814.B13067-0100000@mhc.mtholyoke.edu>
- Mime-Version: 1.0
- Precedence: bulk
-
-
- On Fri, 29 Jul 1994 d.oakley.kid0111@oasis.icl.co.uk wrote:
-
- > Windows in Dialogs is in my list because programs like Interface
- > allow you to have modal dialogs in windows or just dialogs. The
- > advantage of not using dialogs is speed - when you are updating
- > 20 items and have to bring up a dialog for each one, the small
- > wait involved while the window draws can get annoying.
-
- That must depend on code speed. I can't see any noticeable difference in
- opening a windowed dialog vs. a regular dialog under Geneva (that's on an
- 8mhz 68000). I would guess that if someone else's code is slow, that can
- be improved.
-
- > This is all up for debate but things like that are usually saved in the
- > program's own preferences file, and I take it that APP_DEFS conforming
- > programs will not use their own preference files: Am I right or wrong?
-
- I disagree. Programs like Geneva and NeoDesk keep a substancial amount of
- additional information (everything from a program_flag list for Geneva to
- dialog_positions for NeoDesk). I doubt you would want an APP_DEFS file
- overwhelmed by all that application specific stuff.
-
- --
- Rick Flashman, Gribnif Software Tel 413.247.5620
- P.O. Box 779, Northampton, MA 01061-0779 Fax 413.247.5622
- For customer support/information please email "gribnif@genie.geis.com".
-